\documentclass[12pt]{article}
\usepackage[top=2.5cm, bottom=2.5cm, left=2.5cm, right=2.5cm]{geometry}
\begin{document}
\begin{center}
\section*{Meeting Notes}

Embedded Systems Team

Chris Hale, Manager

16 Sept 2010, 3:30pm
\end{center}

\subsection*{Attendance}
The entire team was present:
\begin{enumerate}
\item
Chris Hale
\item
Martin Young
\item
Evan Arnold
\item
Edmund Chu
\end{enumerate}

\subsection*{Progress}
\begin{enumerate}
\item
Since our last meeting on the 9th, we have successfully been able to install the Sun SPOT Manager application to install on various systems:
\begin{itemize}
\item{Windows 7 32bit, 64bit is not supported}
\item{Mac OS X 10.4 and 10.6}
\item{Ubuntu Linux 10.04}
\end{itemize}
\item
We also got the emulator to work. We can interact with a virtual Sun SPOT and load in \textit{midlets}, programs for the Sun SPOTS emulator.
\item
We talked to Paul Monaghan about the problem of installing the Sun SPOT base station on the virtual server currently set up. Our remedy will be to take over one of the lab computers to interface with our base station. It will effectively become a secondary server that will pass commands back to the virtual Ubuntu server that the DB and UI teams will be using.
\end{enumerate}

\subsection*{Week's Decisions and Tasks}
\begin{enumerate}
\item
Finish documentation to install Sun SPOT software and drivers. Then test documentation by following instructions on a clean system to ensure its validity.
\item
Independently work with the emulator and SDK to read room temperatures from an emulated Sun SPOT.
\begin{enumerate}
\item
Provide documentation on discoveries or breakthroughs about using the emulator and SDK so that they may be shared amongst the team.
\item
No need to commit code to our code repository just yet, although code should be kept as it will become useful once we figure out our code structure (API design).
\end{enumerate}
\item
We may need to offload [temporary] storage to the base station. In other words, the Sun SPOTs may need to send the raw data they collect and the base station will temporarily store, analyse, and package this information.
\item
Think about the API design as we dive into the Sun SPOT SDK and understand what it is capable of.
\end{enumerate}

\subsection*{Future Work/Roadmap and Adjustments to Plan}
\begin{enumerate}
\item
By the first integration, we need to create a framework for sending data to the database, even if that data is just dummy data.
Currently waiting on DB to provide network code for pushing data to the database.
\begin{enumerate}
\item
This means we will need to design our API, but this can only be done once we better understand the Sun SPOT SDK.
\end{enumerate}
\item
Determine how to use the additional features of the Sun SPOT, including: movement, light sensor, LEDs, push buttons.
\item
Although we talked with Paul Monaghan, we have not yet determined which lab computer to take over.
This decision can be delayed until we move our code from the emulation to the real world.
\item
No adjustments to plan, only elaboration.
\end{enumerate}

\subsection*{Notes}
\begin{enumerate}
\item
In the Advanced Computer Lab, the lights turn off automatically when no motion is detected.
We could exploit this feature: For the client, this means they will know if the room is being occupied, not just simply if the lights are on or off.
\item
We will probably end up with two separate programs: One for the \textit{midlit} (Sun SPOT), the other for the base station.
\end{enumerate}

\end{document}